This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
>Yes, i think it's permission is high enough. In one of the Edits i wrote that for example >MSXML2.DOMDocument Interface is working fine.
Reading 'EDIT2' of your original post, I understand that you succeeded in calling out to MSXML2.DOMDocument from the same agent. If that is true, then yes, agent permissions seem to be o.k.
>Only my dll seems to have a problem. However, since the DLLs works from Notes and a Test >Program on the same server, it seems not to be a general a problem of my DLL. Maybe >Domino just cannot find it.
If I recall correctly, LotusScript -- no matter whether it is executed from Notes or from Domino -- utilizes the usual mechanism to find COM servers. I.e., it looks them up in the Windows Registry. If your "MyComDll.Interface" is properly registered, then Domino should find the DLL, just like Notes -- when running on the same machine -- seems to find it.
>Is there a way to get more detailed error infos from the domino console? It would be very >interesting to know WHY it cannot create the object. :)
None I am aware of => Domino admins in this forum, what do you think?
Maybe there is some Windows tool to spy into COM => Windows aficionados in this forum, what do you think?
>I also tried to remove all UI components from my dll.
Seems like we can rule out that as a potential cause as well.
Well, I guess I'm running out of ideas for the time being.
Feedback response number JSAK9SRBLT created by ~Chris Frofootherobu on 01/14/2015
Hmmm
Return to top
. . . . . . Hmmm (~Fred Asatumibu... 14.Jan.15) 
